we need docs here:

For all new functionality we require tests to ensure they continue to work as intended. For bug fixes we require a test to cover the bug fix (if one didn't exist yet).

rextendr

• we use testthat to test functionality
• avoid adding new snaptshots whenever. snapshot tests are not indiciative of behavior

extendr-api

Two types of tests:

• rust test
  • see https://github.com/extendr/extendr/tree/main/extendr-api/tests for non-module-specific tests
  • do not use doc tests
  • otherwise include tests in a test module at the bottom of the module file
  • use test! macro see example https://github.com/extendr/extendr/blob/c1651f52dd94fdd56424d73b0b1951d3b94a364b/extendr-api/src/conversions/try_into_int.rs#L111
  • use with_r(|| {}) tests see https://github.com/extendr/extendr/blob/c1651f52dd94fdd56424d73b0b1951d3b94a364b/extendr-api/src/iter.rs#L246
• integration tests—these are to test the interface between rust and r these live in {extendrtests} package
  • particularly required for optional feature and integrations, handling of data across ffi bounds etc
  • see https://github.com/extendr/extendr/blob/c1651f52dd94fdd56424d73b0b1951d3b94a364b/tests/extendrtests/
  • example:
    • rust functions :https://github.com/extendr/extendr/blob/c1651f52dd94fdd56424d73b0b1951d3b94a364b/tests/extendrtests/src/rust/src/tuple_conversions.rs
    • called from testthat tests https://github.com/extendr/extendr/blob/c1651f52dd94fdd56424d73b0b1951d3b94a364b/tests/extendrtests/tests/testthat/test-tuples.R#L57

use the justfile to help run these with just document then just devtools-test and for rust tests just test and then also ensure that things are formatted with just fmt

extendr-internals : lets add a callout note coming soon!

send it?

send it!

OH man i think you deleted the CNAME!